-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release-test.yml: Add strasbourg creds [backport 2023.10] #20013
release-test.yml: Add strasbourg creds [backport 2023.10] #20013
Conversation
(cherry picked from commit ad0edec)
This is needed before the spelling fix... |
Can't you just add the spelling fix to this? Speeds up the process a bit. |
git cherry-pick -x 51ee3b64dcde618eaa415a55aa331ec6024a6be7 ;-) |
Small typo fix... stasbourg -> strasbourg (cherry picked from commit 51ee3b6)
I didn't think it would need a backport but it seems like the release manager script triggers the workflow of the RC and not of master... |
Yes, why would use the master? |
Triggering manually does it and also that would have solved my immediate problem 😎 |
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Backport of #20007 and #20008
Contribution description
This adds creds for stasbourg needed for the
openmote-b
tests in the release specs.Testing procedure
Hmmm... I don't know how easy it is. I will try to link results of the workflow from my personal fork maybe?
Issues/PRs references
Needed for RIOT-OS/Release-Specs#289